Neon Pricing
Pricing plans that grow with you. From prototype to Enterprise.
Neon pricing plans
- 1 project
- 0.5 GiB storage
- Autoscaling up to 2 CU
- Community Support
- Pay via marketplace AWS
- 100 projects
- 10 GiB storage included
- 300 compute hours included
- Autoscaling up to 4 CU
- Point-in-time restore (7 days)
- Standard Support
- Pay via marketplace AWS
- 1,000 projects
- 50 GiB storage included
- 750 compute hours included
- Autoscaling up to 8 CU
- Point-in-time restore (14 days)
- Standard support
- Get migration help
- 5,000 projects
- 500 GiB storage included
- 1000 compute hours included
- Higher compute capacity
- Point-in-time restore (30 days)
- Private Link
- Datadog integration
- Migration assistance
- Compliance (GDPR, SOC 2, ISO)
- 99.95% SLA
- Priority support
Explore the .
Custom Enterprise Plans
Connect with our team for higher resource limits, dedicated requirements, annual contracts, and more.
Neon billing fundamentals
An architecture with branch-based storage and compute that autoscales
Storage
Branches = copies of data + schema
Database branches in Neon feel like "database copies", but they are ready instantly and they do not cost you extra storage.
Thousands of branches, same storage cost
All branches in a project share the same storage. 100 GB in Neon feels like a lot more—you can "copy" that dataset hundreds of times, e.g. for dev & test.
Compute
You only pay for the compute you use
Neon autoscales in response to your workload—you get more capacity when you need it, and pay less when traffic is slower.
"Compute you use" = "compute hours"
is how we measure compute usage. Example: a 4 CU compute running for 20 hours uses 80 compute hours.
Detailed plan comparison
Find the plan that fits your needs, or reach out to us for custom Enterprise plans.
- Included
- Storage
- Compute hoursCompute hours = CU size x active hrs
- Projects
- Branches
- Databases
- Compute Features
- Max compute size
- 0.5 GiB
- 190 /month
- 1
- 10
- 500 per branch
- 2 CU
- 10 GiB
- 300 /month
- 100
- 500 per project
- 500 per branch
- 4 CU
- 50 GiB
- 750 /month
- 1,000
- 500 per project
- 500 per branch
- 8 CU
- 500 GiB
- 1,000 /month
- 5,000
- 500 per project
- 500 per branch
- 10 CU
Branching is as useful as we hoped it would be. Our testers can now play with features earlier, since we can now stage features, requiring different database migrations, in parallel.
Frequently Asked Questions
Compute hour is the metric for compute usage in Neon. The quick math: [compute hours] = [compute size] x [hours your compute runs]. Each pricing plan includes a certain number of compute hours; how quickly you consume these hours depends on the size of your compute and how long it runs. Once you exceed the allocated amount of compute hours, you'll be billed for overages in a given month.
In Neon, you are charged a monthly fee (corresponding to your pricing plan) plus any additional compute and/or storage usage over the limits included in your plan. For example, the Launch plan includes 300 compute-hours of compute usage; if you consume 320 compute-hours in a month, you will be billed additionally for 20 compute-hours.
Neon bills for the past month's usage at the beginning of each calendar month. For more information, see Manage billing.
You can get a good idea by estimating how many hours your databases run, and at which compute size. For example: imagine you’re running a 2 CPU, 8 GB RAM database for 2 hours a day (or 62 hours per month). This equals [2 CU * 62 hours] = 124 compute hours per month.
When enabling autoscaling, you will set a maximum autoscaling limit (e.g. 2 CU) that will act as a de-facto cost limit.
Neon implements a unique storage engine that enables database branching on copy-on-write, without duplicate storage. You can create instant database copies (database branches) without adding to the storage bill. Since Neon retains database history, the size of storage for a Neon project will be calculated as the size of your tables plus the WAL up to the configurable history retention period. Read more in our docs.
Yes, we display your usage consumption in the Neon admin console and we will also email you when you’re getting close.
Neon implements usage limits for branching in order to prevent potential abuse of the service which can negatively impact other users. For customers seeking higher limits please contact customer-success@neon.tech.
The Business plan is our most affordable and feature-complete option for teams with existing production workloads. This plan is designed to fit all the production use cases that are popular among our customers, including large production applications with variable traffic, SaaS with database-per-user at scale, developer/BaaS platforms, dev/test workflows, and AI Agents. Explore our Case Studies to learn more. We also do Enterprise contracts to accomodate unique requirements—reach out to us to inquire about it.
Still have questions?
Interested in learning more about our plans and pricing? Complete the form below to get in touch with our Sales team.
Talk to Sales